address duplication in subscribers list
Hi,
I have a lot of duplicates in my subscribers addresses.
I use mlmmj-sub to subscribe addresses, and it seems that this command don't check if the address already exists before subscribing it ! Is it a bug or a missing fonctionnality ?
Marc
Quoted 8 lines · Marc Delpont
Hi,
I have a lot of duplicates in my subscribers addresses.
I use mlmmj-sub to subscribe addresses, and it seems that this command don't check if the address already exists before subscribing it ! Is it a bug or a missing fonctionnality ?Marc
Hi Marc,
I had the same issue and it was due to the fact I was using an old version.
See the discussion here http://mlmmj.org/archive/mlmmj/2015-05/0000003.html
Signature · 2 lines
GPG : 0x3A7DDABC985EDC6E Blog: http://axilleas.me
Quoted 8 lines · Achilleas Pipinellis
Quoted 7 lines · Marc Delpont
Hi,
I have a lot of duplicates in my subscribers addresses.
I use mlmmj-sub to subscribe addresses, and it seems that this command don't check if the address already exists before subscribing it ! Is it a bug or a missing fonctionnality ?
Quoted 7 lines
Quoted 1 line
Marc
Hi Marc,
I had the same issue and it was due to the fact I was using an old version.
See the discussion here http://mlmmj.org/archive/mlmmj/2015-05/0000003.html
I'm using version 1.2.18 that is the last stable debian package, and is not a so old version !
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Quoted 15 lines · Marc Delpont
Le 05/10/2015 13:22, Achilleas Pipinellis a écrit :
Quoted 14 lines · Marc Delpont
Quoted 8 lines
Hi,
I have a lot of duplicates in my subscribers addresses. I use mlmmj-sub to subscribe addresses, and it seems that this command don't check if the address already exists before subscribing it ! Is it a bug or a missing fonctionnality ?
Marc
Hi Marc,
I had the same issue and it was due to the fact I was using an old version.
Quoted 7 lines
Quoted 3 lines
See the discussion here
http://mlmmj.org/archive/mlmmj/2015-05/0000003.htmlI'm using version 1.2.18 that is the last stable debian package, and is not a so old version !
If you read the discussion I had the same problem and I had to use apt pinning to upgrade to a latest version where this bug is fixed.
- --
GPG : 0x3A7DDABC985EDC6E
Blog: http://axilleas.me
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJWEmz7AAoJEBTqGDGsMtXM/BgP/1Po3Uz9Nunqm4UppCPsh6rB K7n1SiXs6sDztt48gzqz7olxY9s7rbi3mDa7gJmXhLfeY+fWiLuEpeqSvmIlOCQF Q3cTrbujZ9rpg3a33KD4ABB1NegimfF/BisRJLoV8z79RFo4M89Ap81byb305Enh JuymUh2/3feSpz3xChAWDVB3cSJcQBcI1SEbmE+T7tqWDtp92OYyqePuCzKa+t+e O+zuK4ID9J+3HW0v20cwFqw9xrjIoAiAe2HFe7tgXRRTzdUxO/W+kgjkx+pI5V2G sLCq/lOHSICwDTqLkI5kEG3tg0S6yFGOEHIs0rhzEb17/xNhq5zRbTqZitj+E7XS dmXaRFdGD5scCE9yxis1zHGS8CUCgRDtJWeHr7lL4MLjHE4Q+yvTaexVd4VfJfFg eU/TmXvzfWMd0h4LgCOIq3ruMEFiK7X8tKJtmGLyQeZWHoCcRXSECCsPdT5KBn2L VYo0Z+8u0zR8mLlSYbWBstYqI04JdMY5WHU4LeEnEbPL1JyAjKjGoUjabSDK0/+3 7d1RV2e3VBLSNtETsqOFhsGE2OVOh0g2XkO0I3iHjsuBWVND+2miUSpZ7IPpwHzs QTx1Jlkv7/nHKLK2SPjoZlBtPbJ+9SPmkXfxtaxInzFYLlRYPWX73VSBx0cP8BhU mZ+p9QbvFD7ZAZFVBLUY
=zR2P
-----END PGP SIGNATURE-----
Marc Delpont:
Quoted 2 lines
I'm using version 1.2.18 that is the last stable debian package, and is not a so old version !
using the latest package from $os-vendor does not mean using the current version:
http://mlmmj.org/hg/mlmmj/file/RELEASE_1_2_19_0/ChangeLog#l11
Andreas
unsubscribe me
Quoted 17 lines · A. Schulze
Marc Delpont:
I'm using version 1.2.18 that is the last stable debian package, and is
Quoted 2 lines
not a so old version !
using the latest package from $os-vendor does not mean using the current version:
http://mlmmj.org/hg/mlmmj/file/RELEASE_1_2_19_0/ChangeLog#l11
Andreas
Signature · 9 lines
*Ryein C. Goddard* System Administrator, Software Engineer, & Consultant. Phone – (971) 599-3501 We can be reached from 9 AM to 5 PM PST If you have an after hours emergency, off-hour rates may apply.
A. Schulze :
Quoted 8 lines
using the latest package from $os-vendor does not mean using the current version:
http://mlmmj.org/hg/mlmmj/file/RELEASE_1_2_19_0/ChangeLog#l11
Andreas
Thanks for this precision !
I was just pointing out that the penultimate revision of the last version can't seriously be considered as an "old" version.
Marc
Marc Delpont:
Quoted 7 lines
A. Schulze :
Quoted 6 lines
using the latest package from $os-vendor does not mean using the current version:
http://mlmmj.org/hg/mlmmj/file/RELEASE_1_2_19_0/ChangeLog#l11
Quoted 7 lines
Quoted 2 lines
Andreas
Thanks for this precision !
I was just pointing out that the penultimate revision of the last version can't seriously be considered as an "old" version.
That depends on your point of view. Your report was "hey this is broken", but it's been fixed "upstream" more than a year ago and Debian *Oldstable* (Wheezy) version doesn't have the fix. From that point of view, Debian Oldstable's version is old. Debian Stable (Jessie), Testing (Stretch) and Unstable (Sid) all have mlmmj 1.2.8.1-1 which should have the fix.
It is possible to fix in Debian Stable and Oldstable, but the rules for those releases is that they can only get *important* fixes, not new versions... so to fix this someone would need to come up with the minimal patch required to fix the bug and submit it to a bug report. Then the maintainer could upload that fix as "mlmmj-1.2.8-1+deb8u1" to a pending-proposed-updates repository, which will then get incorporated into the distribution on the next "point release" of that distribution. (Usually every 3 months or so.) I don't think this particular bug would be considered worth going through all this.
The easiest way around all this would be to backport the package for Wheezy and put it into an external repository. I just did this (because I'm likewise running mlmmj on Wheezy), so if you want it, it's available here:
http://debian-packages.coredump.us
direct link if you just want the .deb files than to add the repo:
http://debian-packages.coredump.us/debian/pool/main/m/mlmmj/
-- Chris
Signature · 2 lines
Chris Knadle [email protected]